Practical Software Architecture: Moving From System Context to Deployment by Tilak Mitra

Author:Tilak Mitra [Mitra, Tilak]
Language: eng
Format: epub
Tags: computers, Software Development & Engineering, General
ISBN: 9780133763126
Google: EbbxCgAAQBAJ
Publisher: IBM Press
Published: 2015-11-18T00:32:04.883550+00:00

Figure 8.15 COM for the Elixir system with identified DUs.

The PDUs are as follows:

• U_Browse_RTV—A PDU that allows corporate customers access to the real-time visualization interfaces.

• U_Browse_Reports—A PDU that allows corporate customers access to the suite of business intelligence reports and their visual user interfaces.

• U_Priv_Browse_RTV—A PDU that allows corporate employees access to the real-time visualization interfaces.

• U_Priv_Browse_Report—A PDU that allows corporate employees access to the suite of business intelligence reports and their visual user interfaces.

The DDUs are as follows:

• D_KPI_Insert_Local—A DDU that represents the KPI data entity generated by the CN_RTAP node.

• D_KPI_Insert_Aggregate—A DDU that represents rolled-up KPI values aggregated to each cycle of machine operations. This entity is persisted in the CN_EDW node.

• D_Rule_Output_Insert—A DDU that represents the data entity encapsulating the outcome of triggered business rules executed on the CN_BRMS node.

• D_Machine_Data_Ingest—A DDU that encapsulates a message packet that enters the CN_RTAP node.

• D_WorkOrder_Insert—A DDU that represents a work order item that gets created in the CN_WOMS node.

• D_Machine_FailureMode—A DDU that represents an entity that gets retrieved from the CN_RCM node.

The EDUs are as follows:

• E_Browse—An EDU that is capacity sized to host the PDUs in the service centers.

• E_Priv_Browse—An EDU that is capacity sized to host the PDUs in the corporate offices.

• E_Create_KPI—An EDU that is capacity sized to meet the service-level requirements of the CN_ODS node.

• E_Process_KPI—An EDU that is capacity sized to meet the service-level requirements of the CN_RTAP node.

• E_Trigger_Rule—An EDU that is capacity sized to meet the service-level requirements of the CN_BRMS node.

• E_Generate_Report—An EDU that is capacity sized to meet the service-level requirements of the CN_RS node.

• E_Process_SignOn—An EDU that is capacity sized to meet the service-level requirements of the CN_PS node.

• E_Process_Auth—An EDU that is capacity sized to meet the service-level requirements of the CN_DS node.

• E_KPI_Transfer—An EDU that is capacity sized to meet the service-level requirements of the CN_DTS node.

Note that no EDUs are identified for the nodes in the Back Office Zone. The reason is that the nodes in this zone already exist as a part of the corporate IT landscape, and hence, no further definition and design for its placement and capacity sizing are required. Again, I tried to keep things as simple as possible—a mantra that I can chant as long as it may take for it to become imprinted into your architect DNA!

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.